Workflow automation at a multifunction printer via a composite document

ABSTRACT

A composite document comprises a publicly posted composite document including a plurality of parts, a map-file for each participant in a workflow associated with the composite document, and a set of encryption keys. The encryption keys are associated with at least one of the plurality of parts and distributed via the map file to the participants. At least one of the parts of the composite document, associated with the encryption keys, includes workflow processing instructions. The workflow processing instructions are enactable by the multifunction printer independent of a server and automate at east some steps of the workflow for participant at the multifunction printer via resident functions of the multifunction printer.

BACKGROUND

With the advent of the information age, the volume of documents thathave been created, stored, communicated has grown dramatically, whilethe complexity and variety of different types of documents hasexperienced equally robust growth. Furthermore, documents are often nolonger used as unitary elements that are native to their specificformats. Instead, a typical use, e.g. a presentation, often involvesusing documents of a variety of different formats e.g. portable documentfile, word processor file, spreadsheet file, slide presentation file,portable audio file, video file, etc. These documents can be gatheredtogether to represent a collection of documents, which we call acomposite document. The secure creation, management, use, monitoring anddisposal of such documents are a significant part of enterprise documentlifecycles.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram schematically illustrating a compositedocument, according to one example of the present disclosure.

FIG. 2 is a block diagram schematically illustrating a set of encryptionkeys, according to one example of the present disclosure.

FIG. 3 is a block diagram schematically illustrating example parts of acomposite document, according to one example of the present disclosure.

FIG. 4 is a block diagram schematically illustrating a diagram regardingdifferential access to parts of a composite document, according to oneexample of the present disclosure.

FIG. 5A is a block diagram schematically illustrating a control portion,according to one example of the present disclosure.

FIG. 5B is a block diagram schematically illustrating a documentmanagement system, according to one example of the present disclosure.

FIG. 6A is a diagram schematically illustrating a workflow, according toone example of the present disclosure.

FIG. 6B is a block diagram schematically illustrating a printerprocessing instruction, according to one example of the presentdisclosure.

FIG. 6C is a block diagram schematically illustrating a type componentassociated with a printer processing instruction, according to oneexample of the present disclosure.

FIG. 7A is a diagram schematically illustrating event-based triggers toenact printer processing instructions, according to one example of thepresent disclosure.

FIG. 7B is a diagram schematically illustrating temporal-based triggersto enact printer processing instructions, according to one example ofthe present disclosure.

FIG. 8 is a block diagram schematically illustrating a multifunctionprinter, according to one example of the present disclosure.

FIG. 9 is a flow diagram schematically illustrating an access protocol,according to one example of the present disclosure.

FIG. 10A is a block diagram schematically illustrating an actioncomponent associated with a printer processing instruction, according toone example of the present disclosure.

FIG. 10B is a block diagram schematically illustrating a propertiescomponent associated with a printer processing instruction, according toone example of the present disclosure.

FIG. 11 is a flow diagram schematically illustrating a method ofautomating participant workflow at a multifunction printer, according toone example of the present disclosure.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings which form a part hereof, and in which is shown byway of illustration specific examples in which the disclosure may bepracticed. It is to be understood that other examples may be utilizedand structural or logical changes may be made without departing from thescope of the present disclosure. The following detailed description,therefore, is not to be taken in a limiting sense.

At least some examples of the present disclosure at least partiallyautomate workflow at a multifunction printer by guiding a workflowparticipant through portions of the workflow and/or by the multifunctionprinter acting as a workflow participant to execute some of the actionsthat might otherwise ordinarily be performed by a human participant. Indoing so, at least some examples of the present disclosure takeadvantage of the structure and security of publicly-posted compositedocuments (PPCDs) by embedding workflow processing instructions into thePPCDs. In one aspect, the embedded workflow processing instructionsincrease compliance and/or effectiveness of the human participants inthe workflow.

In at least some examples of the present disclosure, a compositedocument comprises a PPCD including a plurality of parts, at least onemap-file for each participant in a workflow associated with thecomposite document, and a set of encryption and signature keys embeddedin each corresponding map file. Individual keys are associated with eachof the plurality of parts. At least one of the parts of the compositedocument includes workflow processing instructions or printer processinginstructions (PPI).

In one aspect, the workflow processing instructions are enactable by themultifunction printer to automate at least some tasks that wouldotherwise be performed by a human participant at the multifunctionprinter, or to guide the human participant through the tasks, byemploying resident functions of the multifunction printer.

In another aspect, access to the workflow processing instructions islimited to assigned, credentialed multifunction printer(s) while accessis excluded for other, non-assigned multifunction printers lackingcredentials.

In some examples, the full set of all encryption keys provides fullaccess to the PPCD. A subset of the full set of keys provides for apartial access to at least one part the document, depending on which keyor keys are provided. Each workflow participant is provided with a setor subset of the keys that correspond to the level of access assigned tothat particular participant. In one aspect, each “assigned”multifunction printer is also considered to be a workflow participantand therefore, is provided with a subset or full set of keys.

At least some examples of the present disclosure dramatically decrease aparticipant's time spent at a multifunction printer to accomplish theirassigned workflow tasks and/or dramatically increase the effectivenessof the overall workflow.

In another aspect, some types of potential human errors are eliminatedwhile performing tasks at the multifunction printer. Some examples ofhuman errors overcome via at least some examples of the presentdisclosure include; a) missing or forgetting to perform some workflowsteps, such as forgetting to upload a copy of a scanned document toorganization's record management system; and b) mistyping documentdestination information, such as sending a document from a multifunctionprinter to a wrong destination.

In another aspect, via at least some examples of the present disclosure,many workflow tasks have been automated and thereby save the user fromtedious user input through a device's control panel.

For example, many times after a workflow participant prints a document,they also send the document via email to another person. In atraditional workflow, the participant is expected to affirmatively takeseveral actions to do so. First, the participant is expected to rememberto email the document to another person, to remember the email address,and to correctly type the email address into the control panel at themultifunction printer. Even if the email address is conveniently alreadyin a directory accessible via the multifunction printer, the participanttypically has to make several key strokes to find the desired emailaddress and properly select that email address while avoiding aninadvertent selection of an adjacent email address.

However, via at least some examples of the present disclosure, many ofthese actions are already automated via the printer processinginstructions that are already embedded within the PPCD. Accordingly,upon enactment of the printer processing instructions at themultifunction printer, many actions formerly performed by a workflowparticipant are now performed by the multifunction printer and/or madesimpler by the multifunction printer.

For example, in the case where the workflow indicates that theparticipant is to send (via email) a signed document to anotherindividual, the printer processing instructions already would have thecorrect email address (for the intended recipient) securely embeddedinto the PPCD to enable the email to be retrieved. Accordingly, theparticipant would be saved from the effort of typing in the intendedrecipient's email address and there would be no chance of selecting thewrong email address or mistyping the email address, and the participantwill not need to remember to send the document and thus will not forgetto do so.

Moreover, upon completion of the participant's tasks, the workflow atthe multifunction printer would automatically initiate sending the emailto the intended recipient, thereby avoiding a chance that theparticipant would forget to do so, or intentionally not do so. Inaddition, upon completion of sending the email, the multifunctionprinter can automatically send a notification to others (besides theindividual) in the workflow indicating that the email was sent to theintended recipient, such that the system operating the workflow does nothave to rely on the individual's memory or willingness to do so.

Because it is known to those establishing the workflow that theseactions will be taking place as well as knowing who the participantsare, where they are located, etc., the efficiency and effectiveness ofthe workflow is greatly enhanced by embedding within the PPCD theprinter processing instructions to automatically perform (orautomatically elicit) such actions associated with an individualparticipants role in the workflow.

It will be understood that the foregoing examples of enhanced workflow,via at least some examples of the present disclosure, are merelyrepresentative of just some of the types of automated workflow producedvia printer processing instructions embedded within the PPCD. Rather,many other aspects of enhanced workflow occur via at least some examplesof the present disclosure, some of which are described and/orillustrated below.

Accordingly, these examples, and additional examples, are furtherdescribed and illustrated in association with at least FIGS. 1-11.

FIG. 1 is a block diagram schematically illustrating a publicly-postedcomposite document (PPCD) 10, according to one example of the presentdisclosure. As shown in FIG. 1, the PPCD 10 includes a plurality ofparts 12 (such as parts A, B, C, etc.) and at least one map-file 16 foreach participant in a workflow associated with the composite document.In one aspect, with multiple participants in a workflow, and with onemap-file for each participant, the PPCD 10 includes an array 14 ofmap-files 16. In another aspect, each map-file 16 includes a keyset 18corresponding to the level of access assigned to that particularparticipant for a particular part (A, B, C, F, C, etc.) of the PPCD 10.

In some examples, the keyset 18 includes a full set of encryption keys,a subset of encryption keys, or no encryption keys.

FIG. 2 represents the encryption keys that can form part of keyset 18(FIG. 1). As shown in FIG. 2, in one example, the keys 40 available toform keyset 18 include an encryption key (E), a decryption key (D), asignature key (S), and a verification key (V), with the particular setof keys (i.e. keyset 18) associated with a map-file 16 depending uponthe level of access granted to that particular participant for aparticular part of the PPCD 10.

In some examples, in the context of a workflow associated with a PPCD10, differential access is provided among multiple workflow participantsand provided for parts of a PPCD 10 via at least the array 14 of mapfiles 16 and encryption keys. In some examples, such differential accessis implemented via at least some of the features and attributes as thedifferential access, map files, and encryption keys for PPCDs, aspreviously described and illustrated in association with: DifferentialAccess for Publicly-Posted Composite Documents with Multiple WorkflowParticipants, (Proceeding, Doc Eng'10, Proceedings of the 10^(th) ACMSymposium on Document Engineering, Pages 115-124, ACM, New York, N.Y.©2010).

As further shown in FIG. 1, at least one of the parts 12 includesprinter processing instructions 32, which are enactable by amultifunction printer. The printer processing instructions 32, whenenacted by the multifunction printer, automate at least some steps of aworkflow (as represented by workflow automation indicator 34) at themultifunction printer via resident functions of the multifunctionprinter.

In some examples, the multifunction printer enacts the printerprocessing instructions without the assistance of and/or withoutreceiving commands from, a server, at least because the instructions areprovided via the PPCD 10. Accordingly, the multifunction printer enactsthe printer processing instructions independent of a server, i.e.without a server.

In one aspect, access to the printer processing instructions isavailable to assigned multifunction printers for which credentials areestablished and access is prevented (to the printer processinginstructions) for non-assigned, non-credentialed multifunction printers.Accordingly, the printer processing instructions will not be enactableby those non-assigned, non-credentialed multifunction printers.

In some examples, within this framework, each PPCD 19 includes a jobidentifier and a signature to ensure that execution is limited toauthorized print jobs.

FIG. 3 is a block diagram schematically illustrating parts of a PPCD 10,according to one example of the present disclosure. At least forpurposes of employing printer processing instructions in at least someexamples of the present disclosure, and as shown in FIG. 3, parts 12 ofthe PPCD 10 include at least a workflow print eligible part 60 and aworkflow print non-eligible part 64. In general terms, each workflowprint eligible part 60 corresponds to printer recognizable file formats62, i.e. file formats that the multifunction printer is equipped torecognize and handle. In one aspect, this ensures that the multifunctionprinter is equipped to enact the printer processing instructions, whichaim to utilize resident functionalities of the multifunction printer. Insome examples, the workflow print eligible part(s) 60 of a PPCD 10include, but is not limited to, at least one of a printable format of atext or word processor file, a spreadsheet, an image file (e.g. JPEG,PNG, etc.), a hypertext markup language (HTML) file, a portable documentformat (PDF) file, a Printer Command Language (PCL) file, a Postscript(PS) file, etc.

In general terms, the workflow print non-eligible part(s) 64 of the PPCD10 are not printable at the multifunction printer (at least for theparticular state in which the PPCD 10 arrives at the multifunctionprinter) and need not have a file format recognizable by themultifunction printer. Accordingly, the workflow print non-eligiblepart(s) 64 are generally unrestricted regarding their file format.Workflow print non-eligible parts can be handled on the device as partof a composite document that are intended for printing.

In some examples, the print processing instructions comprise a “workflowprint non-eligible” part 64 of the PPCD 10 because they will not beprinted at the multifunction printer.

In some examples, the part of the PPCD 10 that contains printerprocessing instructions 32 is a text-based file, and is expressed in acomma-separate values (CSV) file, XML, or other pre-defined formatsuited to providing printer processing instructions in a mannerconsistent with at least some examples of the present disclosure, in oneexample, the printer processing instructions 32 (FIG. 1) comprise astring including at least one non-executable keyword component, asfurther described later in association with at least FIG. 6B, in someexamples, the string takes the form of a metadata structure.

FIG. 4 is a diagram schematically illustrating a table 100 thatrepresents differential access among multiple workflow participants todifferent part(s) of the PPCD 10, according to one example of thepresent disclosure. As shown in FIG. 4, in some examples, table 100includes rows 102 listing different workflow participants 111, 112, 113,114 and columns 104 listing different parts (A, B, C, F, G, H) of a PPCD10. For any given workflow participant and any given part, table 100expresses the type of access (No Access, Read Only Access, and ModifyAccess) granted. In addition, table 100 expresses which keys implementthat level of access. For example, as expressed in Table 100, a ReadOnly Access corresponds to the subset of keys including a verificationkey (V) and a decryption key (D). Meanwhile, a Modify Access correspondsto the full set of keys including an encryption key (E), decryption key(D), a signature key (S), and a verification key (V). In this way, table100 represents the manner in which map-files establish the differentialaccess that the workflow participants 111, 112, 113, 114 have to variouspart(s) A, B, C, F, G, H of the PPCD 10.

In at least some examples, as shown in Table 100 of FIG. 4, one workflowparticipant 114 includes or is defined by a multifunction printer andone part of the PPCD 10 includes or is defined by printer processinginstructions (PPI) enactable by the same multifunction printer 114. Inone aspect, such a multifunction printer can be referred to as a MFPworkflow participant 114.

In some examples, as expressed in Table 100, a Read Only Access isprovided to the MFP workflow participant 114 at least because theprinter processing instructions (PPI) are not changeable by themultifunction printer 114 yet the multifunction printer 114 will accessthem to be able to enact the printer processing instructions as part ofthe desired workflow. Details regarding the mechanics of suchauthentication and/or enactment by the MFP workflow participant) of theprinter processing instructions are further described later inassociation with at least FIGS. 6A-11. Moreover, the manner in which theMFP workflow participant generally participates in the work flow alsowill be further described later in association with at least FIGS.6A-11.

It will be understood that in at least some examples, a workflow willinclude multiple multifunction printers with at least some of thosemultifunction printers acting as workflow participants. In one aspect,the participation of the respective multifunction printers is spacedapart over time and/or distance. In some instances, the workflow willinterleave activity of other workflow participants (i.e. humans) betweenand among the MFP workflow participants.

FIG. 5A is a block diagram schematically illustrating a control portion160, according to one example of the present disclosure. In someexamples, control portion 160 includes a controller 162, a memory 164,and a user interface 166.

In general terms, controller 162 of control portion 160 comprises atleast one processor 163 and associated memories that are incommunication with memory 164 to generate control signals directingoperation of at least some components of the systems and componentsdescribed throughout the present disclosure. In some examples, thesegenerated control signals include, but are not limited to, automating aworkflow at a multifunction printer via printer processing instructionsembedded securely within a PPCD 10. In some examples, a control portion160 is present in the multifunction printer at which the printerprocessing instructions are enacted and/or at which the multifunctionprinter acts a workflow participant. In some examples, a control portion160 is present in a document management system that establishes andfacilitates the PPCD 10 and/or its workflow. In some examples, a controlportion is present in resources that engage, or that is engaged by, thePPCD 10 along the workflow. Accordingly, as the PPCD 10 moves throughvariety of secure and non-secure environments as part of its workflow,the PPCD 10 is subject to and/or interacts with at least some portionsof a control portion 160.

In particular, in response to or based upon commands received via a userinterface 166 and/or machine readable instructions (including software),controller 162 generates control signals to at least partially implementthe general workflow in accordance with at least some of the previouslydescribed examples and/or later described examples of the presentdisclosure. In one example, controller 162 is embodied in a generalpurpose computer while in other examples, controller 162 is embodied inother resources associated with the workflow.

For purposes of this application, in reference to the controller 162,the term “processor” shall mean a presently developed or futuredeveloped processor (or processing resources) that executes sequences ofmachine readable instructions (such as but not limited to software)contained in a memory. In some examples, execution of the sequences ofmachine readable instructions, such as those provided via memory 164 ofcontrol portion 160 cause the processor to perform actions, as operatingcontroller 162 to generate a PPCD 10, enact printer processinginstructions, and/or provide and operate portions of a workflow asgenerally described in for consistent with) at least some examples ofthe present disclosure. The machine readable instructions may be loadedin a random access memory (RAM) for execution by the processor fromtheir stored location in a read only memory (ROM), a mass storagedevice, or some other persistent storage (e.g., non-transitory tangiblemedium or non-volatile tangible medium, as represented by memory 164. Inone example, memory 164 comprises a computer readable tangible mediumproviding non-volatile storage of the machine readable instructionsexecutable by a process of controller 162. In other examples, hard wiredcircuitry may be used in place of or in combination with machinereadable instructions (including software) to implement the functionsdescribed. For example, controller 162 may be embodied as part of atleast one application-specific integrated circuit (ASIC). In at leastsome examples, the controller 162 is not limited to any specificcombination of hardware circuitry and machine readable instructions(including software), nor limited to any particular source for themachine readable instructions executed by the controller 162.

In some examples, user interface 166 comprises a user interface or otherdisplay that provides for the simultaneous display, activation, and/oroperation of at least some of the various components, functions,features, and of control portion 160, a multifunction printer, and/orother workflow resources, as described throughout the presentdisclosure. In some examples, at least some portions or aspects of theuser interface 166 are provided via a graphical user interface (GUI).

Moreover, it will be understood that the features, functions, modules,and components of the PPCD 10 (including the printer processinginstructions) and associated workflow modalities, such as multifunctionprinter (e.g. multifunction printer 282 in FIG. 6A), as describedthroughout the disclosure can be arranged in different forms andgroupings, and therefore the PPCD 10 (FIG. 1) and various modalities(e.g. multifunction printer 262 in FIG. 6A) are not strictly limited tothe particular arrangement or groupings of functions, modules, andcomponents illustrated in FIGS. 1A-10.

FIG. 5B is a block diagram schematically illustrating portions of adocument management system 200, according to one example of the presentdisclosure, storable in memory 164 and operable via a control portion160 as previously illustrated in association with FIG. 5A. As shown inFIG. 5B, in one example the document management system 200 includes acomposite document generation apparatus 202 and a communication module204. In general terms, the composite document generation apparatus 202generates PPCDs 10 having at least the characteristics and parameters asthose described in association with FIGS. 1-11.

With this in mind, in some examples, composite document generationapparatus 202 generates a PPCD 10 including a plurality of parts with atleast a first part including printer processing instructions 232 to atleast partially provide for workflow automation 234 for authorizedparticipants at a multifunction printer.

In one aspect, the printer processing instructions 32 are enactable viathe multifunction printer without the assistance of a server and/orwithout receiving commands from a server, thereby providing server-lessworkflow automation at the multifunction printer.

Moreover, in some examples, to ensure the security of the PPCD 10, atleast a portion of the printer processing instructions 232 arenon-executable (by a processor) and, at least via their association withthe encryption keys, the printer processing instructions 232 areembedded within, and form an inseparable part, of the PPCD 10. Inaddition, via at least these same protections, the printer processinginstructions cannot be altered or eavesdropped. In one aspect, as withother PPCDs, part tables, and all other tables are also signed toenforce authenticity of the document and those signatures areautomatically verified by the multifunction printer according to thestandard PPCD access protocol

In some examples, the communication module 204 is provided tocommunicate the PPCD 10 externally of the document management system 200to enter a workflow, which includes but is not limited to, enactment ofthe printer processing instructions 232 at the multifunction printer, asfurther described later in association with at least FIG. 6A.

FIG. 6A is a diagram 250 schematically illustrating a workflowenvironment 252, according to one example of the present disclosure. Inone example, workflow environment 252 operates in a manner at leastconsistent with the PPCD 10 and related elements, as previouslydescribed and illustrated in association with FIGS. 1A-5B. As shown inFIG. 6A, the workflow environment 252 includes a document managementsystem 200 that generates a PPCD 10 which enters and at least partiallydefines a workflow (represented by arrow W). In one aspect, it will benoted that workflow environment 252 does not intend to represent acomprehensive or closed environment, but rather is merely representativeof just some examples and aspects in which a workflow can incorporate aPPCD 10 having printer processing instructions (PPI). Furthermore theworkflow is not necessarily enclosed in one organization and can crossorganizational boundaries, non-secure domains and be transferred overnon-secure channels.

As shown in FIG. 6A, as part of the workflow W, authorized participants260, 262 interact with the PPCD 10 via modalities 270 adapted totransmit, receive, store, and/or manipulate the PPCD 10 with eachparticipant participating to the extent authorized by the documentitself. It will be understood that the modalities 270 illustrated inFIG. 6A are merely samples and do not represent the full range ofmodalities by which a PPCD 10 proceeds along workflow W. A PPCD can beaccessed on a laptop, desktop, or other device, USB, EMAIL, LAN andCLOUD can be used as transmission mechanisms. Nevertheless, in someexamples, the modalities shown in FIG. 6A include but are not limitedto, storage interactions (e.g. USB devices 272), network interactions(e.g. LAN) 276, communication interactions 274 (e.g. email), andcloud-based interactions 278.

As further shown in FIG. 6A, at some point in the workflow W, the PPCD10 arrives at multifunction printer (MFP) 382. In one aspect, the PPCD10 includes printer processing instructions (for at least partiallyautomating workflow) that are enactable by the multifunction printer 282to increase compliance and/or effectiveness of the human participants inthe workflow.

As such, the multifunction printer 282 is formally designated as a MFPworkflow participant (114 in FIG. 4) and therefore is associated with atleast one map-file and a subset of encryption keys to enable themultifunction printer 282 to interact with parts of a PPCD 10. Moreover,it will be recalled that the printer processing instructions compriseone of the parts of the PPCD 10, and therefore are embedded in the PPCD10 in an encrypted form, as reflected via their presence in Table 100 inFIG. 4.

In one aspect, the multifunction printer 282 is itself a workflowparticipant that performs actions involving or affecting the PPCD 10 inthe workflow W with the printer processing instructions addressing (butnot limited to): which actions are to be taken by the multifunctionprinter, and when and how to take those actions; and/or when, where, andhow the multifunction printer will facilitate a human workflowparticipant to take specified actions in the workflow.

Accordingly, in one aspect, as a workflow participant the multifunctionprinter 282 acts as a resource by which a participant 280 (a human oranother device) can participate in the workflow (W) at the multifunctionprinter (MFP) as dictated by the printer processing instructionsembedded in the PPCD 10.

More specific examples and aspects of the manner in which the printerprocessing instructions are structured and/or dictate the workflow (W)at the multifunction printer 282 are further described and illustratedin association with at least FIGS. 6B-10B and at least some of thepreviously described aspects and examples of the present disclosure.

It will be further understood that while PPCD 10 may include a pluralityof embedded printer processing instructions, which are defined within asingle part or multiple different parts of the PPCD 10, these multipleprinter processing instructions all relate to accomplishing the samegeneral workflow W and therefore, the multiple printer processinginstructions occur in a coordinated fashion whether they are enactedserially, in parallel, or other pattern.

FIG. 6B is a block diagram schematically illustrating printer processinginstructions 350, according to one example of the present disclosure. Asshown in FIG. 6B, in some examples, each printer processing instruction(PPI) 350 comprises a structure, such as a text-based string 351including at least an action component and a properties component, whichare further described later in association with at least FIGS. 10A and10B. In some examples, the part of the PPCD 10 that contains printerprocessing instructions 32 is a text-based file, and is expressed in acomma-separate values (CSV) file, XML, or other pre-defined formatsuited to providing printer processing instructions in a mannerconsistent with at least some examples of the present disclosure. In oneexample, the printer processing instructions 350 include at least someof substantially the same features and attributes as the printerprocessing instructions 32 (FIG. 1A), 232 (FIG. 5B), as previouslydescribed in association with at least FIGS. 1-6B. It will be furtherunderstood that in at least some examples, the PPCD 10 includes multipleprinter processing instructions 350.

In some examples, as further shown in FIG. 6B, the string 352 that atleast partially defines the printer processing instructions 32, 232further includes a type component, which is further described andillustrated in association with FIG. 6C.

In one example, a representative structure of one printer processinginstruction (that includes a type component, an action component, and aproperties component) can appear as a string, such as“on-completion$$upload document$$\\record-management.hp.com”. In oneexample, the string defines a metadata structure within the PPCD 10.

In one example, this printer processing instruction is enactable by themultifunction printer and dictates that upon completion of an earlieraction(s) (“on-completion”—a TYPE), the document will be uploaded(“upload_document”—an ACTION) to a specified destination(“record-management.hp.com”—a PROPERTY). Finally, it will be understandthat this example string is merely representative of a wide variety oftypes, actions, and properties that can define printer processinstructions (PPI) as part of at least partially automating a workflowin at least some examples of the present disclosure. As a result of suchinstruction, when the participant accomplishes their task at themultifunction printer (e.g. prints some document parts and signs outfrom the device) a copy of the document is automatically uploaded by thedevice into the specified destination (“record-management.hp.com” in theabove example.

More details regarding the type component, action component, andproperties components of a printer processing instruction are providedin association with at least FIGS. 6C-10B.

FIG. 6C is a block diagram schematically illustrating a type component360 of a printer processing instruction, according to one example of thepresent disclosure. In one aspect, the type component comprises featuresand attributes that are at least consistent with previously describedexamples relating to a type component and/or printer processinginstructions.

In general terms, the type component 360 specifies a context in which arespective one of the printer processing instructions will be accessed(via compliance with an access protocol for a PPCD) and enacted at (orby) the multifunction printer. However, in some examples, a printerprocessing instruction omits a type component, but does include othercomponents, such as an action component and a properties component,which are further described later in association with at least FIGS.10A-10B.

In one example, as shown in FIG. 6C, the type component 360 comprises atleast one of a temporal parameter 362 and an event parameter 364.

FIG. 7A is a diagram schematically illustrating implementation of theevent parameter 364 of the type component 360 in a workflow W, accordingto one example of the present disclosure. In some examples, as shown inFIG. 7A, portions 380 of workflow W proceed according to event parameter364 by which at least some of the printer processing instructions aretriggered for execution based on an event involving the multifunctionprinter 282. While a large variety of different types of events canoccur at the multifunction printer involving the PPCD 10, FIG. 7Aillustrates just a few representative examples of events. Accordingly,as shown in FIG. 7A, the workflow W includes events 386, 387, 388.

As shown in FIG. 7A, in one example, at least a portion of the workflowW includes the event of the PPCD 10 arriving at the multifunctionprinter (“ON JOB ARRIVAL” event 386), which is specified via the typecomponent 360 of a printer processing instruction 350. In some examples,upon the arrival of the PPCD 10 at the multifunction printer (i.e. anevent), an action component of printer processing instructions dictatesthat the multifunction printer automatically sends an email to aworkflow participant (already designated in the printer processinginstructions) informing them of the job arrival. In one example, theemail instructs the user to come to the multifunction printer 282 toaccess the PPCD 10 and participate in the workflow. More comprehensivedetails regarding the structure and operation of an action component ofprinter processing instructions are further described later inassociation with at least FIG. 10A.

In one aspect, with further reference to FIG. 7A, when a PPCD 10 arrives(event 386) at the multifunction printer 282, before a correspondingaction takes place (as directed by printer processing instructions),some initial handling steps are taken by the multifunction printer 282.To do so, as shown in FIG. 8, the multifunction printer 400 (282 in FIG.7A) includes an I/O PPCD Filter 430, which performs initial handling ofthe incoming PPCD 10 via sorting the PPCD-type files from other types offiles.

In some examples, this initial handling includes the I/O PPCD filter 430authenticating the PPCD 10 and automatically verifying the printerprocessing instructions. In some examples, the I/O PPCD filter 430 alsorecognizes any time-based printer processing instructions, which arethen decrypted and uploaded to scheduler 432 of multifunction printer(400 in FIG. 8; 282 in FIG. 7A). In one aspect, the PPCD 10 is thenstored in a designated directory in the memory 414 of the multifunctionprinter 400 (FIG. 8), which is a restricted access directory, which inturn is accessible via authentication of the workflow participant at themultifunction printer. The part of the printer processing instructionsthat are uploaded to scheduler 432 can be removed or otherwise marked asused/deployed.

Accordingly, after the incoming PPCD 10 is sorted from other incomingjobs, and without the parts of the PPCD 10 being engaged directly, themultifunction printer 282 stores the PPCD 10 in the memory 414 of themultifunction printer 400 until the stored PPCD 10 is called for as aportion of the remaining workflow W.

Once the incoming PPCD has been properly handled, a printer processinginstruction including an ON ARRIVAL event 486 is enacted at or by themultifunction printer, such as the earlier described example of sendingan email to notify a workflow participant that the PPCD 10 has arrivedat the multifunction printer. In one aspect, the ON ARRIVAL-type printerprocessing instructions are immediately enacted upon the multifunctionprinter automatically and immediately engaging a PPCD access protocol,as will be further described later in association with at least FIG. 9.

With further reference to FIG. 7A regarding the type component of theprinter processing instructions, in some examples, a portion of theworkflow W includes a participant accessing the PPCD 10 (ON USER ACCESSevent 387) via a control panel or user interface 416 of themultifunction printer 400 (FIG. 8). In some examples, the user ispresent at the user interface 416 because the user was previouslyprompted via email (see ON JOB ARRIVAL event) of the presence of thePPCD 10 at the multifunction printer 282, and therefore, the user hasapproached the user interface 416 to participate in the workflow.

On the other hand, one example of the ON USER ACCESS event 387 includesa participant loading the PPCD 10 into the memory 414 (FIG. 8) of themultifunction printer via a USB memory device.

In either case, before a participant can perform workflow tasksinvolving the PPCD 10, the human participant (as a requester) willengage a PPCD access protocol at user interface 416 of multifunctionprinter 400, as shown in FIG. 8.

FIG. 9 is a flow diagram 451 of at least some portions of a PPCD accessprotocol, according to one example of the present disclosure. Thisaccess protocol generally applies either to a multifunction printer as aworkflow participant or applies to a human workflow participant thatseeks access to parts of the PPCD 10. In short, a requester includes aparticipant seeking access to a part of a PPCD 10. Accordingly, fordiscussion purposes at least in association with FIG. 9, either type ofparticipant is referred to as a requester.

As shown in FIG. 9, the PPCD access protocol initiates an authentication454 that challenges the requester to supply credentials such as usernameand password as part of a login 456. In one aspect, this authentication454 is supported by or involves a LDAP server. In some examples,authentication 454 is omitted from the protocol.

If the requester is successfully authenticated, the requester's privatekeys are fetched as represented at 460. In some examples, access keysare accessed from a portable memory resource, such as a smart card, USBmemory device, or local in-device key store.

In the case where the requester is a human participant, a status 462 isreported to the user via a pop-up notification at the user interface 416regarding whether their private keys have been successfully retrievedand whether such keys will successfully access the part(s) of the PPCD10.

If the requester's keys are correct, then access is granted to parts ofPPCD 10 to which the requester (whether human or MFP) has been assignedkeys (Table 100 in FIG. 4). However, if the requester's keys areincorrect, then access is denied to the parts of PPCD 10.

For human requesters, a status 468 of allowed or denied access isreported via a pop-up notification at the user interface 416 in FIG. 8.In some examples, the status regarding allowed or denied access also iscommunicated (e.g. via email) to others (e.g. supervisor, colleague,etc.) to inform them of an attempted, but denied access or an attempted,successful access. Besides helping to manage a workflow, such statusreports enhance security of the PPCD 10.

A process of a multifunction printer, as a requester, accessing a partin the PPCD 10 also follows generally the same steps (authentication,key retrieval and access) as for a human requester except that, with themultifunction printer as a requester, the initial authentication isperformed automatically and directly between the multifunction printerand the PPCD 10. As noted above, in some examples authentication 454 isomitted.)

On the other hand, when a human requester engages the PPCD accessprotocol, at least some manual steps would be performed at the userinterface 416 of multifunction printer 400 (282 in FIG. 7A) such asentering a login name and entering a password.

Accordingly, except for some level of automation when the multifunctionprinter attempts access, the manner in which a human requester or amultifunction printer (as a requester) engages the initial portion 465of the PPCD access protocol is generally the same.

As further shown in FIG. 9, a query at 417 signals a transition topotential enactment of printer processing instructions. In particular,the case in which the decrypted/accessed part of the PPCD 10 is not aprinter processing instruction (PPI) corresponds to a workflow for ahuman participant. As shown at 472 in FIG. 9, the user can print thedocument at the multifunction printer or take other available actions(e.g. digital send) according to whatever instructions the user alreadyhad in possession about their role in the workflow.

On the other hand, as represented at 474 in FIG. 9, in the case wherethe decrypted/accessible part of the PPCD 10 is a printer processinginstruction (PPI), then the multifunction printer automatically enactsthe printer processing instruction(s) 350.

Having set forth some of the mechanics of securely accessing printerprocessing instructions before enacting the printer processinginstructions, additional examples are provided regarding the featuresand attributes of the ON ACCESS event 387 of type component 360 of aprinter processing instruction.

In some examples, the action component of the particular printerprocessing instructions call for the multifunction printer tocommunicate to the human workflow participant which workflow tasks toperform. In one example, the PPCD 10 includes placeholders for insertionof documents to be scanned by the workflow participant. Accordingly, viathe ON USER ACCESS event 387, upon the user accessing the PPCD 10, oneaction includes prompting (at the user interface 416 in FIG. 8 or viaemail notification) the participant to obtain or supply a document andthen scan that document at the multifunction printer. For example, ifthe workflow involved financial matters such as a mortgage application,the pop-up notification would instruct the user retrieve a copy of theirW2 yearly income record and scan that W2 record, which thenautomatically becomes a part of the PPCD 10. In other words, the PPCD 10automatically directs the multifunction printer to integrate the scanneddocument into the PPCD 10 at the placeholder.

In one example, the workflow is further automated by instructing theuser to authorize the MFP to append a digital signature (available fromthe memory 414 of the MFP) to the PPCD 10. This action avoidstraditional cumbersome process of the user printing a document,physically signing it, and the scanning the document.

In some examples, the multifunction printer will be notified anytimethat a signature is called for on a document (from a part of the PPCD10) so that the multifunction printer can automatically add the usersdigital signature to the PPCD 10, after timely engagement with the PPCDaccess protocol.

In one example, via the ON ACCESS event 387 in the printer processinginstructions, upon the user accessing the PPCD 10, user interface 216causes a pop-up notification displaying a listing of the parts orsubparts of PPCD 10 for which the user can initiate an action at themultifunction printer, such as requesting printing.

As a general matter, and also applicable specifically regarding an ONACCESS event associated with a printer processing instruction, fulldecryption does not take place until just before the specified actionwill be taking place. This timing helps to maintain security over theprinter processing instructions and/or the contents of the PPCD 10itself and part of the PPCD 10 being handled at or by the multifunctionprinter at that time.

FIG. 7A further schematically illustrates a further type component of aprinter processing instruction, namely an ON COMPLETION event 388,according to one example of the present disclosure.

In one example, with further reference to FIG. 7A, an ON COMPLETIONevent 388 occurs upon a participant meeting a workflow milestoneestablished by the printer processing instructions. For example, themilestone could be completion of all requested actions for a particularparticipant or for that multifunction printer (when it acts as aworkflow participant). For example, a few representative samplemilestones could include a participant scanning all requested documents,adding all requested electronic signatures, and/or sending the updatedPPCD 10 to a particular addressee. Additional examples of actionsassociated with an ON COMPLETION-type event are further described laterin association with at least FIGS. 10A, 10B.

FIG. 7B is a diagram of a portion of a workflow W in association withthe temporal parameter 362 of the type component 360 of a printerprocessing instruction, according to one example of the presentdisclosure, in one example, as further shown in FIG. 7B, portion 390 ofworkflow W proceeds according to temporal parameter 362 in which atleast some of the printer processing instructions are enacted based ontemporal factors.

In particular, as shown in FIG. 7B, in one example, at least a portionof the workflow W is automatically executed or triggered based on anabsolute time factor (ABSOLUTE factor 392) such as (but not limited to)a time of day, day of the week, time and date, etc. In some examples,this ABSOLUTE factor exhibits a repeating behavior such as a time/dayoccurring each week, which is represented by the indicator INTERVAL. Insome examples, the ABSOLUTE factor occurs a single time for a given PPCD10 or for a given multifunction printer.

Accordingly, when the particular temporal occasion occurs (per ABSOLUTEfactor 392), the printer processing instructions will commence an actionto be performed automatically by the multifunction printer or an actionin which the multifunction printer guides or instructs a user to performa workflow task. In some examples, such guidance or instruction takesthe form of an email, pop-up notification at a user interface of themultifunction printer, etc.

As further shown in FIG. 7B, in some examples, at least a part of theworkflow W is automatically executed or triggered based on a relativetime factor (RELATIVE factor 394) of temporal parameter 362 of typecomponent 360 of a printer processing instruction. In some examples, theRELATIVE time factor includes a time period preceding, coinciding with,or following an event E (or an absolute time factor ATF). In oneexample, as shown in FIG. 7B, a printer processing instructionspecifying a RELATIVE factor 394 for a temporal parameter 362 of thetype component 360 (of a printer processing instruction) is executed ortriggered upon an elapsed time period (ELAPSED TIME) following an event.

In some examples, aspects of the event parameter 364 and the temporalparameter 362 of the type component 360 of a printer processinginstruction are combined or cooperate along generally the same portionof a workflow W or different portions of a workflow W.

In one example, the temporal parameter 362 of the type component 360 ofa printer processing instruction leverages the operation of thescheduler 432 (FIG. 8) of the multifunction printer. In some examples,to facilitate a user performing a task that is part of the workflow,such as scanning a document possessed by the user, the printerprocessing instruction includes the action of sending an email to theuser every fifteen minutes until/unless the user performs the requestedworkflow task. In this situation, the temporal parameter 364 of the typecomponent 360 of a printer processing instruction 350 causes themultifunction printer to automatically perform actions to facilitate thework flow, such as tracking the time intervals via a scheduler of themultifunction printer to perform the action of monitoring the status ofwhether another action (e.g. scanning a document) was performed or not.In another aspect, this example illustrates how one of the residentfunctions (e.g. scheduler 432) of the multifunction printer is leveragedto deploy printer processing instructions.

In some examples, upon entry of the PPCD 10 to the multifunction printer400 at the I/O PPCD filter 430 and in coordination with scheduler 432,each printer processing instruction is time stamped with its time ofarrival. Via the temporal parameter 362 of type component 360, one ofthe printer processing instructions can specify an action that themultifunction printer notifies a workflow participant (via email orpop-up notification) within a certain time period (ELAPSED time) fromthe time of arrival of the PPCD 10. In some examples, the temporalparameter 362 of type component 360 also can be employed to specify anevent as an elapsed time after an action (i.e. workflow task) performedby the workflow participant.

The examples described and illustrated in association with Figure aremerely representative of a wide variety of ways to employ the temporalparameter 362 and/or event parameter 364 of a type component of aprinter processing instruction in accordance with at least some examplesof the present disclosure.

FIG. 10A is a block diagram schematically illustrating an actioncomponent 500 of printer processing instructions 358 (FIG. 6B),according to one example of the present disclosure. In general terms, asshown in FIG. 10A, the action component comprises a keyword reference502 to invoke at least one application programming interface (API) 504(of a plurality of application programming interfaces of themultifunction printer) to perform an action dictated by the printerprocessing instructions of the PPCD 10.

In some examples, a family of printer processing instructions include aclosed library of a fixed number of keywords, which provides one aspectof security, as each action will have a corresponding unique keyword,and actors outside of workflow W will not have knowledge of thosekeywords. However, in some examples, some of the keywords includeadditional unnecessary characters or symbols to obscure the content ofthe keyword.

In some examples, keywords for an action component include keywords suchas upload, store, send, sign, etc. In one aspect, a limited vocabulary(e.g. fixed set) of keywords is employed. In some examples, each keywordis related to a workflow task and/or resident function of themultifunction printer.

In some examples, the keyword is non-executable to ensure security ofthe action component and the printer processing instruction, as a whole.Moreover, the keyword is further secured via being a portion of theembedded, encrypted printer processing instructions (PPI).

In some examples, the action component forms part of a printerprocessing instruction without a specified type component (FIGS. 8A-8C).In some examples, the action component specifies an action in relationto or in response to a specified type per type component 360 (FIG. 8A).

As further shown in FIG. 10A, the action component 500 includes an arrayof application programming interfaces (API) 504. In one aspect, at leastsome of the respective application programming interfaces correspond toor define at least some of the resident functions of the multifunctionprinter. In some examples, at least some of the application programminginterfaces include (but are not limited to) a transmit API 508, astorage API 510, a user interface API 412, end/or a job processing API514.

In general terms, the transmit/receive API 508 includes (but is notlimited to) functions which transmit or receive part of a PPCD 10 (orsubparts of a document) or other information. Accordingly, in someexamples, the transmit/receive API 508 includes functions or actionssuch as facsimile communications, email directly to/from themultifunction printer, data upload, etc.

In general terms, the storage API 510 includes (but is not limited to)functions or actions which relate to storage of parts or subparts of aPPCD. In some examples, the storage API 510 tracks, and/or controls,storage to disk, storage to a USB memory device, retrieval from memory,etc.

In general terms, the user interface API 512 includes (but is notlimited to functions or actions which relate to the user interface(s) ofthe multifunction printer. Accordingly, in some examples, the userinterface API 512 includes such functions or actions such as pop-upnotifications of a control panel that request further information;indicate a status; confirm completion of an action; etc.

In general terms, the job processing API 514 includes (but is notlimited to) functions or actions which relate to the job processingperformed on some parts of the PPCD by the multifunction printer.Accordingly, in some examples, the job processing API 514 includes suchfunctions or actions such as printing documents, scanning documents,appending or authorizing a digital signature for a part or the wholePPCD 10, etc.

In one example of the present disclosure, the at least partiallyautomated workflow at the multifunction printer includes the action ofapplying a digital signature to a part of a PPCD 10. In this way, byincorporating the digital signature into the PPCD 10, a great deal oftime and effort is saved as compared to traditional methods of obtainingsignatures. In a traditional workflow, to obtain a signature theparticipant would print a part of document (e.g. word processingdocument), physically sign it with ink, and then scan the physicallysigned document. Sometimes, further additional steps of navigatingdirectories and other commands follow the actual scanning.

However, via at least some examples of the present disclosure, the jobprocessing API 514 enables directly applying a previously obtaineddigital signature (stored at the multifunction printer) to parts of thePPCD 10. This action saves numerous workflow steps because the documentpart need not be printed, need not be physically signed, and/or need notbe scanned to become incorporated into the PPCD 10. Rather, in at leastsome examples, the printer processing instructions automate the workflowvia directly and automatically retrieving the digital signature at themultifunction printer and apply it appropriately to the PPCD 10.Alternatively, the workflow is at least partially automated by sending anotification to a participant to apply the digital signature to the PPCD10 at the multifunction printer.

FIG. 10B is a block diagram schematically illustrating a propertiescomponent 530 of printer processing instructions (FIG. 7), according toone example of the present disclosure. In general terms, as shown inFIG. 10B, the properties component 530 further specifies an aspect ofthe action component to establish the detailed logistics of executingthe intended action in the workflow. In some examples, the propertiescomponent 530 of a printer processing instruction (PPI) includes (but isnot limited to) a destination parameter 532 (e.g. location where to senda scanned document or signed document), a storage location parameter 534(e.g. where a document is coming from or where a document is going to),a temporal parameter (e.g. when), display data selection parameter 538(e.g. how or what to display), or a scan settings parameter 540 (whatscan settings to implement). It will be understood that these parameters532-540 are merely representative of the types of properties that can bespecified for an action of a printer processing instruction.

FIG. 11 is a flow diagram 601 schematically illustrating a method 600 ofat least partially automating workflow at and/or by a multifunctionprinter, according to one example of the present disclosure. In someexamples, the method 600 is performed via the systems, modules,components, functions, etc. as previously described and illustrated inassociation with FIGS. 1-10B. In some examples, the method 600 isperformed via systems, modules, components, functions, etc. other thanthose previously described and illustrated in association with FIGS.1-10B.

In some examples, in a manner consistent with at least the descriptionassociated with FIG. 5A, the method 600 is stored as machine readableinstructions within a non-transitory computer readable medium and thatare generally executable by or on a processor of a multifunctionprinter.

In some examples, at 602 method 600 includes providing a publicly postedcomposite document (PPCD) that includes a plurality of parts, at leastone map-file for each participant in a workflow associated with thepublicly posted composite document, and a set of encryption keysassociated with each one of the plurality of parts and distributed viathe map file to the participants. In some examples, the set includes atleast one of an encryption key, a decryption key, a signature key, and averification key.

In one aspect, at least one of the parts of the PPCD includes printerprocessing instructions.

At 604, method 600 includes receiving the publicly posted compositedocument (PPCD) at the multifunction printer and enacting the printerprocessing instructions via at least one application programminginterface of the multifunction printer to automate at least some stepsof the workflow at the multifunction printer.

At least some examples of the present disclosure at least partiallyautomate workflow at a multifunction printer by guiding a workflowparticipant through portions of the workflow and/or by the multifunctionprinter acting as a workflow participant to execute some of the actionsthat might otherwise ordinarily be performed by a human participant. Indoing so, at least some examples of the present disclosure takeadvantage of the structure and security of publicly-posted compositedocuments (PPCDs) by embedding workflow processing instructions into thePPCDs.

At least some examples of the present disclosure dramatically decrease aparticipant's time spent at a multifunction printer to accomplish theirassigned workflow tasks and/or dramatically increase the effectivenessof the overall workflow.

Although specific examples have been illustrated and described herein, avariety of alternate and/or equivalent implementations may besubstituted for the specific examples shown and described withoutdeparting from the scope of the present disclosure. This application isintended to cover any adaptations or variations of the specific examplesdiscussed herein.

The invention claimed is:
 1. A multifunction printer comprising: aprocessor; and a memory on which is stored instructions that are tocause the processor to: receive a publicly-posted composite document(PPCD), the PPCD including a plurality of parts, a respective map-filefor each of a plurality of participants in a workflow associated withthe PPCD, and a set of encryption keys associated with at least one ofthe plurality of parts and distributed via the map-files to theparticipants, the set including at least two of an encryption key, adecryption key, a signature key, and a verification key, wherein atleast one of the parts, associated with the set of encryption keys,includes workflow processing instructions, and wherein the map-filesidentify differential access to the plurality of parts by theparticipants; and enact the workflow processing instructions to automateat least some steps of the workflow for a participant of the pluralityof participants at the multifunction printer via resident functions ofthe multifunction printer.
 2. The multifunction printer of claim 1,wherein at least one part of the plurality of parts comprises a workflowprint eligible part and at least one other part of the plurality ofparts comprises a workflow print non-eligible part.
 3. The multifunctionprinter of claim 2, wherein the workflow print eligible part includes atleast one of a word processor part, a spreadsheet part, a slidepresentation part, an image part, a hypertext markup language part, anAUTOCAD part, a portable document format part, a video part, or aportable audio file part.
 4. The multifunction printer of claim 3,wherein the workflow processing instructions comprise a text identifierincluding an action component and a properties component.
 5. Themultifunction printer of claim 4, wherein the workflow processinginstructions include a type component, which is further specified by theaction component and the properties component, wherein the typecomponent comprises at least one of an event-based parameter or atemporal parameter.
 6. The multifunction printer of claim 5, wherein thetemporal parameter of the type component comprises a parameter that isto trigger execution of at least some of the workflow processinginstructions based on temporal factors.
 7. The multifunction printer ofclaim 6, wherein the event-based parameter of the type componentcomprises a parameter that is to trigger execution of at least some ofthe workflow processing instructions upon an event associated with thePPCD at the multifunction printer.
 8. The multifunction printer of claim4, wherein the action component comprises a keyword reference to atleast one application programming interface (API) of a plurality ofapplication programming interfaces of the multifunction printer, andwherein at least some of the resident functions of the multifunctionprinter comprise at least some of the respective application programminginterfaces.
 9. The multifunction printer of claim 8, wherein theplurality of application programming interfaces includes at least one ofa transmit/receive API, a storage API, a user interface API, or a jobprocessing function.
 10. The multifunction printer of claim 4, whereinthe properties component further specifies an aspect of the actioncomponent according to at least one of a destination parameter, alocation parameter, a temporal parameter, a display data selectionparameter, or a scan settings parameter.
 11. The multifunction printerof claim 1, wherein the workflow processing instructions, via theirassociation with the encryption keys, are inseparable from the PPCD. 12.A non-transitory computer readable medium storing instructions, whichwhen executed by a processor of a multifunction printer, are to cause toprocessor to: provide a publicly posted composite document that includesa plurality of parts, a respective map-file for each of a plurality ofparticipants in a workflow associated with the publicly posted compositedocument, and a set of encryption keys associated with at least one ofthe plurality of parts and distributed via the map-files to theparticipants, the set including at least one of an encryption key, adecryption key, a signature key, and a verification key, wherein atleast one of the parts includes printer processing instructions, andwherein the map-files identify differential access to the plurality ofparts by the participants; and enact the printer processing instructionsvia at least one application programming interface of the multifunctionprinter to automate at least some steps of the workflow at themultifunction printer.
 13. The computer readable medium of claim 12,wherein the instructions are further to cause the processor to: providethe publicly posted composite document to include, for each publiclyposted composite document, a job identifier and a signature to ensurethat execution is limited to authorized print jobs.
 14. A documentmanagement system, comprising: a composite document generation apparatusthat generates a publicly posted composite document (PPCD), said PPCDincluding: a plurality of parts comprising at least a first partincluding printer processing instructions enactable via a multifunctionprinter, wherein the printer processing instructions at least partiallyautomate a workflow associated with the PPCD; a respective map-file foreach of a plurality of participants in the workflow, wherein themap-files identify differential access to the plurality of parts by theparticipants; and a set of encryption keys associated with at least thefirst part and distributed via the map-files to the participants, theset including at least one of an encryption key, a decryption key, asignature key, and a verification key; and a communication module tocommunicate the PPCD externally of the document management system forenactment of the printer processing instructions at the multifunctionprinter.
 15. The document management system of claim 14, wherein theworkflow processing instructions comprise a metadata structure definingat least a string including at least an action component that comprisesa keyword reference to invoke at least one application programminginterface (API) of a plurality of application programming interfaces ofthe multifunction printer to execute at least a portion of the workflow.